[Emotion][microperf] Separate form max-width variable to its own utility #7948
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
As we've established in #7486, color computations are expensive to recalculate repeatedly and should be memoized where possible. This is fine for component styles (#7529), but our various
euiComponentVariables
utilities are not getting memoized except as part of component styles.euiFormVariables
is particularly chonky and likely bears examining more closely, but in the interim I'm solving this particular microperf irritant by creating a separate utility just to grab themaxWidth
size for components that only need this token (a surprisingly high number).My upcoming EuiComboBox conversion will be utilizing this PR as well for cleaner and more performant code ✨
QA
General checklist